Make GCS_MAVLink base class handle DO_SET_HOME #26683
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This takes advantage of all our vehicles inheriting from AP_Vehicle, which they didn't when the pure-virtual methods on GCS_MAVLink were first created.
I'm not sure this is the correct shape for handling home generally, but given all but one of our vehicles had the relevant methods already on the vehicle class it seems a reasonable improvement.
There's the basic question of whether home is an AHRS thing or an AP_Vehicle thing. While AHRS has been a good place for home, notionally you don't need AHRS to have a home (Tracker kinda-sorta shows that....)
A first step in further unifying home-position behaviour across vehicle types, anyway.